chore(ci): fix failure in detecting compilers in clang-tidy job - #4642
Merged
Conversation
amoeba
changed the title
Member
Author
|
Seems plausible it was caused by https://github.com/conda-forge/ctng-compiler-activation-feedstock/blob/main/recipe/build_scripts.sh#L222-L224 which looks like it just came out. I can reproduce what see in CI with: |
amoeba
marked this pull request as ready for review
July 31, 2026 22:53
lidavidm
approved these changes
Aug 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The clang-tidy job recently started failing.
Last success: https://github.com/apache/arrow-adbc/actions/runs/30502165159/job/90743952843
First failure: https://github.com/apache/arrow-adbc/actions/runs/30596999777/job/91051511466
The error is,
Note that path to
x86_64-conda-linux-gnu-ccis relative to the CWD which is wrong.The difference seems to be:
In a successful run, I see:
In a failed run, I see:
A notable difference between these two environments is that the last working build used
gcc_linux-64=14.3.0whereas the failures started aftergcc_linux-64=14.4.0showed up.